Skip to content

Conversation

@R-Kri
Copy link
Contributor

@R-Kri R-Kri commented Oct 23, 2025

Description

What is the purpose of this pull request?

This pull request:

  • Fixes JavaScript linting errors detected in the automated lint workflow run #18668369216
  • Resolves ENOENT: no such file or directory, open './boop.js' error
  • Resolves stdlib/no-new-array violations in test file

Related Issues

Does this pull request have any related issues?

This pull request:

Changes

  • Replaced './boop.js' with './example.js' in JSDoc example comments in the following files:

    • lib/node_modules/@stdlib/utils/async/for-each-right/lib/factory.js
    • lib/node_modules/@stdlib/utils/async/for-each-right/lib/index.js
    • lib/node_modules/@stdlib/utils/async/for-each-right/lib/main.js
    • lib/node_modules/@stdlib/utils/async/for-each-right/docs/types/index.d.ts
  • Replaced new Array() constructor with array literal and push pattern in:

    • lib/node_modules/@stdlib/math/strided/special/bessely0-by/test/test.main.js

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request?

All modified files have been tested with ESLint and pass linting validation.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

  • Yes
  • No

If you answered "yes" above, how did you use AI assistance?

  • Code generation (e.g., when writing an implementation or fixing a bug)
  • Test/benchmark generation
  • Documentation (including examples)
  • Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure.

I used Claude AI to understand the linting errors, identify the specific issues, and determine the appropriate fix patterns following stdlib conventions. The actual code changes were made manually by me with guidance from Claude on stdlib's coding standards and proper fix implementations.

@stdlib-js/reviewers

- Replace './boop.js' with './example.js' in JSDoc examples
- Replace new Array() with array literal and push in bessely0-by test
@stdlib-bot
Copy link
Contributor

👋 Hi there! 👋

And thank you for opening your first pull request! We will review it shortly. 🏃 💨

Getting Started

Next Steps

  1. A project maintainer will approve GitHub Actions workflows for your PR.
  2. All CI checks must pass before your submission can be fully reviewed.
  3. You'll need to address any failures in linting or unit tests.

Running Tests Locally

You can use make to run any of the CI commands locally from the root directory of the stdlib repository:

# Run tests for all packages in the math namespace:
make test TESTS_FILTER=".*/@stdlib/math/.*"

# Run benchmarks for a specific package:
make benchmark BENCHMARKS_FILTER=".*/@stdlib/math/base/special/sin/.*"

If you haven't heard back from us within two weeks, please ping us by tagging the "reviewers" team in a comment on this PR.

If you have any further questions while waiting for a response, please join our Gitter channel to chat with project maintainers and other community members.

We appreciate your contribution!

Documentation Links

@stdlib-bot stdlib-bot added First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Needs Review A pull request which needs code review. Good First PR A pull request resolving a Good First Issue. labels Oct 23, 2025
@stdlib-bot
Copy link
Contributor

stdlib-bot commented Oct 23, 2025

Coverage Report

Package Statements Branches Functions Lines
math/strided/special/bessely0-by $\color{green}197/197$
$\color{green}+100.00\%$
$\color{green}5/5$
$\color{green}+100.00\%$
$\color{green}2/2$
$\color{green}+100.00\%$
$\color{green}197/197$
$\color{green}+100.00\%$

The above coverage report was generated for the changes in this PR.

@stdlib-bot stdlib-bot added the Math Issue or pull request specific to math functionality. label Oct 28, 2025
Copy link
Member

@kgryte kgryte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after clean-up. Two comments:

  1. The use of sparse arrays in the test file was intentional. Your original proposed change simply densified the arrays which is not what was wanted.
  2. You simply swapped one non-existent filename for another. This is also not desired. I just removed the proposed filename changes.

@kgryte kgryte removed the Needs Review A pull request which needs code review. label Oct 28, 2025
@kgryte kgryte merged commit 2ee3e58 into stdlib-js:develop Oct 28, 2025
28 checks passed
@R-Kri R-Kri deleted the fix-lint-errors branch October 28, 2025 05:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

First-time Contributor A pull request from a contributor who has never previously committed to the project repository. Good First PR A pull request resolving a Good First Issue. Math Issue or pull request specific to math functionality.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix JavaScript lint errors

3 participants